Ah, you mean it stops at the interfaces assign screen during boot? That should only happen if a configured interface is not present for some reason. When it's booted and configured what interfaces do you have assigned?

@nomadmd glad you got it sorted..

@viragomann ah ok so wasnt serious as i thought here i thought i was going to be locked out and be not able to get back in... least i refreshed... learn something new about pfsense every day... learning experience especially for years when using a dlink or a an asus router lol

Other than having additional storage space the SSD is a lot faster than eMMC and has a much higher write life. For some packages that store a lot of logs or cached data locally you would want that. If you haven't seen an issue on the 3100 and plan to use the same config on the 6100 you will likely be fine with the eMMC. Steve

@Neoveo said in My pc isn't DNS resolving but my pfSense box is: DHCP6 Gateway is still showing up as Pending and Unknown. Delete the now pointless gateway.

This is an old topic I know, but there's a doc page now: https://docs.netgate.com/pfsense/en/latest/general/plus.html

@Firewaller1 You do not need to worry about the WAN IP address assignment. It can be DHCP or static. It does not matter. pfSense itself should select WAN as its default gateway. Your concern is only the LAN side and you already have a static IP address for that. I understand that you have a local network where routing is handled by a L3 switch and you have created a routed link between the L3 switch and pfSense. BTW, that’s my choice, too. In a case like that, pfSense does not know anything about your local network. Because of this, you need a gateway to your LAN on pfSense and one or more static routes. Also, pfSense needs to be the default gateway for your local network. In your /30 link, you have two IP addresses, one on L3 switch and one on pfSense. You need to use the pfSense IP address in the default route on the switch. On the other hand, the switch IP address needs to be defined as a gateway on the LAN side of pfSense. This gateway needs to be used in the static routes to your local network. You need one static route for each LAN subnets you want to interface with pfSense. If the local network is in a completely different address space than pfSense, you probably could use a single, more generic, static route. Placing a switch on the WAN side of pfSense is another issue.

It looks like the problem has been fixed, by ACCIDENT! When moving cables around I accidentally unplugged the ISP equipment from power. After equipment rebooted, my pings started to work, my package manager was able to populate. It looks like the pfSense software update confused the ISP hardware? It all seems good now. Thank you for all your help.

Run: du -h /var Then dig deeper into anything that looks too large.

Yeah that does sound like the switch wasn't as separated as you thought.

No, not on Aruba. But it's probably not difficult. The only question would be if the wifi link devices are truly transparent layer2 and can pass LACP packets. If you really need one giant subnet between both sites I would try that first.

@kenpachizerox Boot environments are amazing I have had to use them a couple times. Without boot environments I would have had a bad day. Again, you do need some extra space to support storage for them. [image: 1702600301220-img_20231214_162428521-resized.jpg]

It works great was able to do tests with 23.09 on a fresh firmware install with the new SSD drive and after backpedal back to my other SSD with 23.05.01 as needed for testing firmware. Great deal for use with SG2100. [image: 1702599958871-img_20231214_162428521-resized.jpg]

@jimp Okay, havent had any crashes with any other software upgrades in the past and seems to be working now. Hardware may have crashed when something changed on the software side, i.e. boot loops. It is supermicro, so this is even more likely the cause. Thanks for looking at this, I've been looking at replacing this appliance with a like Netgate appliance, in the future. Thanks again!

@Firewaller1 said in Abrupt WAN Link down: kernel: re0: watchdog timeout Just for reference that is the error that indicates you should be using the alternative re driver.

@stephenw10 Ah that’s interesting. So custom config within packages are Base64 encoded. Nice! @stephenw10 Thanks for the help. decoded the before and after and changes are recognized.

Yes, do not attempt to install packages if the update repo branch is not set to the same version you are running. It probably isn't in your case which is why it's failing to pull in the package list. But you should upgrade to the current version before installing pkgs anyway. You may have to resave the selected update branch or select a different branch and then move back to 'current stable version' to see it.

@yeahmagnets after mac authentication, it worked thank you guys

OK, theoretically you should be able to upgrade to 2.7.2 eventually by upgrading through the various versiopns. However I would not do that. Take this opportunity to reinstall 2.7.2 clean. You can install as ZFS at that point too. Then restore your config into it.

@GiaNN i'll do some other testing because it seems that so It won't send any message besides the test one